Add StatusCode to understand where we are in the game #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add "StatusCode" to the
Schedule
model, piping in data we already get in the Schedule DTO. I'd like to use it in my project downstream.I also add a
GameStatus
enum. Unfortunately, I don't have access to the MLB documentation, so I'm not quite sure if I'm capturing all potential game statuses -- I feel like I at least captured most of them. If we see an unfamiliar status, I just return null.I thought about calling "StatusCode" "GameStatusCode", but I figured that it is clear enough we are already in the "Game" context.
Tested with the console app: